Migrated from history panel legacy branch

After eba8385, plot_results creates a "Results" group in the signal
panel, breaking panel-wide index lookups. Use group-local lookups so
the test is robust against extra groups.

(cherry picked from commit 5e08f9c)
(cherry picked from commit b2c4965)

…cenarios

…get and HTML rendering

…el and related components

…story

…ages and replay actions

…ality

(cherry picked from commit 6807861)

…s and add new history panel entries

Split the history feature into dedicated modules, refresh the GUI wiring and widgets, and update the related tests and translations.

# Conflicts:
#	datalab/locale/fr/LC_MESSAGES/datalab.po
#	doc/locale/fr/LC_MESSAGES/release_notes/release_1.03.po
#	doc/release_notes/release_1.03.md

Follow-up to a review noting that ruff/pylint had not been run on the
History panel refactor after it was split into submodules. Cross-module
access to underscore-prefixed members triggered W0212, plus a batch of
other lint warnings that were addressed without disabling any checks.

Creation actions (new signal/image) were recorded in the history but, unlike process actions, could not be edited, recomputed or reverted. Editing a creation left downstream steps inconsistent. This makes creations first-class history actions: their parameters can be re-edited, the result is recomputed in place (keeping the UUID and downstream references), and the chain cascades correctly.

* [NEW] : Allow editing creation (new_object) parameters via dialog and recompute in place, preserving the output UUID so downstream actions stay linked

* [NEW] : Resolve target panel for UI creation actions so they replay and cascade like compute actions

* [CHG] : add_ui_entry now returns the created HistoryAction, enabling creation output_uuids to be registered for downstream resolution

* [CHG] : Restore/undo without saving now covers creation actions for both single action and full session

* [FIX] : Snapshot creation parameters on edit for proper export/import and revert

…ompute

Edit-mode replay opened parameter dialogs per selected action, each editing its own downstream chain. Overlapping chains caused repeated prompts and inconsistent state. Recompute also stopped at the edited action instead of cascading to the full downstream.

* [FIX] : Process selected actions once via edit_mode_replay_actions, with deduplication, session-order sorting and a re-entrance guard, instead of calling edit_mode_replay per action

* [FIX] : Replay only the selected actions; on param change, recompute in place then cascade fully downstream from the most upstream edited action

* [CHG] : Cancel restores parameter snapshots for already-edited actions

- Introduce derived processing-chain view in the History panel
- Split chains on delete and add step-by-step replay
- Add editable analysis parameters tab for in-place re-run
- Narrow history panel scope for the current deliverable

update_compatibility_states iterated every action item and resolved its uuid
via get_action_from_uuid, which raises when the action is no longer in the
model. During reconnect_chain_after_removal the recompute cascade emits
SIG_OBJECT_MODIFIED (firing refresh_compatibility_items) before the final
repopulate, so the tree transiently references a just-removed action and the
Qt slot crashed with 'Action not found'. Build a uuid->action map once and
skip unresolved items instead of raising; harden get_selected_actions[_or_
sessions] the same way. Add a regression test.

- disable automatic analysis recomputation and wire it to the recompute button.
- update documentation accordingly

History duplication used to clone whole sessions and remap them at the
session level, which left duplicated entries still pointing at the original
objects' UUIDs. The feature is reworked around processing chains: selecting a
session duplicates all its chains, selecting an action duplicates the single
chain that contains it. Every cloned object receives a fresh UUID and all
action references are remapped to the clones, so the result is an independent,
editable and replayable session.

Operation-rooted chains consume an object created outside the chain, so they
cannot be replayed on their own. A synthetic "Initial state" creation head is
prepended per distinct source object to materialize a clone snapshot, making
such chains self-contained.

* [CHG] : Resolve selection to processing chains via build_session_chains
  instead of normalising actions to their parent session
* [FIX] : Assign a fresh UUID to every cloned object and remap all action
  references, fixing duplicated entries still referencing original UUIDs
* [NEW] : Handle Cas A (creation-rooted chain) by duplicating the root
  new_object action as-is so it stays replayable
* [NEW] : Handle Cas B (operation-rooted chain) by prepending a synthetic
  KIND_UI new_object head (empty kwargs/state, output_uuids=[clone])
  recognised as a chain root by build_session_chains
* [TEST] : Update test_history_duplication (scenarios 1-3) and add
  test_history_duplication_cas_a_creation_root and
  test_history_duplication_cas_b_synthetic_head (26 passed)
* [NEW] : Add French translation "Initial state" -> "Etat initial"

A history session now represents exactly one linear processing chain. The
previous read-model split a session into several chains at each creation
action, which detached downstream processing when duplicating a session.

Session boundaries are already decided at recording time (the "start a new
history session?" prompt shown on object creation), so no per-creation
splitting is performed at display time anymore.

	* [CHG] : build_session_chains() now returns a single ProcessingChain per
	  session (root = first action, all actions kept in order)
	* [FIX] : copy_with_uuid_remap() resolves an effective panel string from
	  the action target so new_object output UUIDs are remapped on duplication
	* [CHG] : Remove dead HistoryAction.regenerate_uuid no-op

Clean-up pass on the history panel: remove symbols that had no caller left in
production nor in the test suite. This reduces the maintenance surface without
changing any behaviour.

	* [CHG] : Remove unused add_to_history decorator and its _resolve_self_target
	  helper (never applied anywhere), drop the add_to_history re-export
	* [CHG] : Remove unused add_entry entry-point and its panel delegation
	* [CHG] : Remove dead chain helper collect_downstream_uuids
	* [CHG] : Remove unused HistoryTree.get_selected_actions
	* [CHG] : Remove dead replay helpers edit_mode_replay (singular),
	  view_only_session_replay and show_readonly_param_dialog
	* [CHG] : Remove ~14 dead HistoryPanel delegation methods that duplicated
	  live module-level functions with no caller

The "Generate macro" action of the history panel was permanently hidden
(setVisible(False), "out of current scope"). Remove it entirely together with
its unreachable implementation to reduce the maintenance surface.

	* [CHG] : Remove the generate_macro_action and its HistoryPanel.generate_macro
	  delegation from the history panel
	* [CHG] : Remove the historytools_ops.generate_macro implementation
	* [CHG] : Remove HistoryAction.to_macro_code (only consumed by generate_macro)

The "Restore parameters" toolbar/context action was permanently hidden
(setVisible(False), "out of current scope"). Remove the dead UI entry point and
its unused panel delegation. The underlying replay_restore_actions() branch is
kept as it is still exercised elsewhere.

	* [CHG] : Remove the _restore_selection_action and all its references in
	  create_menu_actions and update_actions_state
	* [CHG] : Remove the dead HistoryPanel.restore_action_params delegation

The "Edit mode" toggle action was permanently hidden (setVisible(False),
superseded by the Replay / Step-by-step launch modes). Remove the dead UI entry
point and its _edit_action attribute. The edit-mode mechanism itself is kept
intact as it is still used by the recompute pipeline (is_edit_mode), the
step-by-step replay and the test suite.

	* [CHG] : Remove the edit_action button, its _edit_action attribute and the
	  now-useless action re-sync branch in toggle_edit_mode

Reflect the removal of the disabled "Generate macro", "Restore parameters" and
"Edit mode" toolbar actions, and document the "New session" and "Step-by-step"
actions that were missing.

	* [CHG] : Update historypanel.rst toolbar list to match the actual actions
	* [CHG] : Drop obsolete UI translation entries (Generate macro, Restore
	  parameters, Edit mode and related strings)
	* [CHG] : Update the French documentation catalog for the history panel

Rename module-level functions, methods and the cross-module panel attributes so
they no longer use the single leading-underscore "private" formalism, in line
with the project coding conventions. This clears the protected-access (W0212)
warnings raised on cross-module usage without introducing any lint suppression.
Property backing fields and purely-internal attributes stay private.

	* [CHG] : Rename private history helper functions to public names
	* [CHG] : Rename private HistoryAction, WorkspaceState, HistoryPanel and
	  HistoryTree methods to public names
	* [CHG] : Expose the cross-module panel flags (edit_replay_in_progress,
	  suppress_session_prompt, session_input_pending) as public attributes

…ssing is interrupted

…y manual flow

- Add `BaseProcessor.recompute_processing()` (+ `ProcessingReport` in processor layer)
- Delegate `apply_processing_parameters()` and `recompute_selected()` 1-to-1 phase to processor API
- Keep panel-only UI refresh logic (properties/processing tab) after successful recompute
- Preserve cross-panel source dispatch and in-place object update semantics
- Align moved comments with original wording for clearer diffs

…ndence

…entry point

Metadata deletion, separate-view creation, and startup side effects could leave object models and remote-control operations inconsistent or make GUI tests depend on shared state. Preserve stable identities, decouple separate views from the main plot cache, and make test-only history tracking and unattended startup behavior explicit.

	* [FIX] : Preserve object UUIDs when deleting metadata so ObjectModel and RPC set_object operations remain coherent
	* [FIX] : Build separate-view items without requiring or mutating the main plot cache
	* [CHG] : Disable HistoryPanel tracking by default in test application contexts and explicitly enable it for history-dependent tests
	* [FIX] : Skip the guided tour during unattended startup while preserving the interactive preference and behavior
	* [FIX] : Add focused regression coverage for metadata identity, remote object updates, separate views, history isolation, and unattended startup

…ability

The History panel had accumulated overlapping responsibilities and broad tests,
making replay workflows harder to maintain and unrelated GUI tests sensitive to
persistent History state. Split the feature into cohesive services, simplified
object lifecycle flows, and replaced oversized coverage with focused behavioral
contracts across supported Python versions.

    * [CHG] : Separate History runtime, UI, navigation, facade, and reconnection
      responsibilities into cohesive components
    * [NEW] : Extract replay UUID mapping and object creation services for reuse
      across duplication, recompute, deletion, and HDF5 import workflows
    * [FIX] : Keep runtime output indexes consistent and preserve plugin
      provenance when replaying or reconnecting objects
    * [CHG] : Replace overlapping History tests with 12 compact behavioral
      contracts and a dedicated visual smoke test
    * [FIX] : Disable History tracking by default in unrelated GUI tests and
      prevent unattended runs from persisting dock or current-tab state

Consolidate the History panel implementation around explicit runtime, navigation,
replay, and persistence responsibilities. This integration also preserves object
identity across metadata and remote-control workflows while isolating GUI tests
from interactive application state.

    * [CHG] : Split History runtime, UI, navigation, facade, and reconnection
      responsibilities into cohesive components
    * [NEW] : Add reusable replay UUID mapping and object creation services
    * [FIX] : Preserve object UUIDs across metadata deletion, remote updates,
      separate views, replay, duplication, and HDF5 persistence
    * [FIX] : Keep action/output indexes and plugin provenance consistent during
      deletion, recomputation, reconnection, duplication, and import
    * [CHG] : Replace overlapping History tests with focused model, workflow,
      navigation, persistence, and visual contracts
    * [FIX] : Isolate unattended GUI tests from History tracking, guided-tour
      startup, dock visibility, and persistent current-tab state

…panel

…existing-rois-instead-of-replacing-them' into develop

…mputation-of-analysis-1-to-0' into develop

Processing errors and user cancellations previously shared the same outcome, causing the recomputation workflow to stop before refreshing eligible analyses. Explicit outcomes now preserve continuation after ordinary errors while stopping only after a genuine cancellation, and analyses remain unchanged until manually recomputed.

	* [FIX] : Distinguish processing errors from user cancellations through explicit computation and processing report states
	* [FIX] : Continue recomputing eligible objects and analyses after processing errors, while stopping the analysis pass after an actual cancellation
	* [NEW] : Cover manual-only analysis refresh after ROI, data, and property changes and strengthen ROI preservation checks with an independent snapshot
	* [CHG] : Synchronize French UI and documentation translations with the clarified manual recomputation behavior

# Conflicts:
#	datalab/gui/panel/base.py
#	datalab/gui/processor/base.py
#	datalab/tests/features/common/auto_analysis_recompute_unit_test.py
#	doc/locale/fr/LC_MESSAGES/release_notes/release_1.03.po

Post-merge auditing exposed cases where plugin provenance could be lost during
History operations, partial recomputation failures could leave outputs in an
inconsistent state, and multi-action edits could replay dependent work more than
once. History execution now preserves feature identity, reports failures
explicitly, and applies dependent updates in a deterministic, transactional way.

* [FIX] : Preserve plugin origins when replaying actions, remapping metadata,
  recomputing transformations, and refreshing analyses
* [FIX] : Stop dependent cascades after failed actions and keep affected
  actions stale while allowing independent branches to continue
* [FIX] : Validate multi-output recomputation before updating objects and
  roll back all outputs when an update cannot be completed
* [FIX] : Isolate multi-object analysis persistence failures, continue with
  remaining objects, and distinguish empty results from failed execution
* [CHG] : Deduplicate and globally order multi-action edits, restore action
  state on cancellation, and cascade analyses after upstream changes
* [NEW] : Add regression coverage for plugin provenance, transactional
  recomputation, cascade failures, and multi-action History edits
* [CHG] : Synchronize French translations for recomputation failure messages